Control device, base station, terminal device, and control method

ABSTRACT

[Object] To provide a control device, base station that reduces the response time of UE by determining a base station in which data on an application is held in advance and by causing the determined base station to hold the data. 
     [Solution] There is provided a control device including: a control unit configured to determine a base station from among a plurality of base stations on the basis of a predetermined condition, the base station causing data on an application used by a terminal device to be linked, the terminal device wirelessly communicating with the base station; and a notification unit configured to notify all base stations determined by the control unit that the data is caused to be linked.

TECHNICAL FIELD

The present disclosure relates to a control device, a base station, aterminal device, and a control method.

BACKGROUND ART

With the development of mobile communication systems, the size of datato be processed by the mobile communication system has also increased.In related art, cache data referred to by a terminal device (userequipment; UE) has been located outside the radio access network (RAN)and evolved packet core (EPC). Thus, it takes time to refer to the cachedata from the UE.

Thus, in recent years, a technique called the mobile edge computing(MEC) has been developed. The MEC is a technique in which cache data oran application is arranged in a base station (eNodeB), and so the cachedata is referred to from UE or an application to be used by the UE areenabled (activated). Thus, it is possible to speed up the response time,which is the time from when an UE requests data to when it receives thedata. Techniques related to the MEC are disclosed in, in one example,Patent Literatures 1 and 2, or the like.

CITATION LIST Patent Literature

Patent Literature 1: JP 2014-531810T

Patent Literature 2: JP 2014-515222T

DISCLOSURE OF INVENTION Technical Problem

However, in the MEC technique in related art, when the UE uses data thathas never been used, data is not cached in a base station, andeventually a longer response time, which is the time taken from when UErequests data to when it receives the data, will be taken. Similarly, ina case where there is an application that is not activated in the basestation, a longer response time will be taken until reception of thedata even when the UE makes a request to the base station using theapplication.

In view of the above, the present disclosure provides a novel andimproved control device, base station, terminal device, and controlmethod, capable of reducing the response time of UE by determining abase station in which application-related data is held in advance and bycausing the determined base station to hold the application-relateddata.

Solution to Problem

According to the present disclosure, there is provided a control deviceincluding: a control unit configured to determine a base station fromamong a plurality of base stations on the basis of a predeterminedcondition, the base station causing data on an application used by aterminal device to be linked, the terminal device wirelesslycommunicating with the base station; and a notification unit configuredto notify all base stations determined by the control unit that the datais caused to be linked.

Further, according to the present disclosure, there is provided a basestation including: an acquisition unit configured to acquire anotification that causes data on an identical application to be linkedwith another base station; and a control unit configured to cause thedata to be linked with the other base station depending on a requestfrom a terminal device on the basis of the notification acquired by theacquisition unit.

Further, according to the present disclosure, there is provided aterminal device including: a control unit configured to notify a corenetwork of information on an application in which data is linked withanother terminal device that communicates with a base station identicalor different to or from a base station which communicates with theterminal device.

Further, according to the present disclosure, there is provided acontrol method including: determining a base station from among aplurality of base stations on the basis of a predetermined condition,the base station causing data on an application used by a terminaldevice to be linked, the terminal device wirelessly communicating withthe base station; and notifying all determined base stations that thedata is caused to be linked.

Advantageous Effects of Invention

According to the present disclosure as described above, it is possibleto provide a novel and improved control device, base station, terminaldevice, and control method, capable of reducing the response time of UEby determining a base station in which data is held in advance and bycausing the determined base station to hold the data.

Note that the effects described above are not necessarily limitative.With or in the place of the above effects, there may be achieved any oneof the effects described in this specification or other effects that maybe grasped from this specification.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram illustrated to describe a configuration example of amobile network system to which the MEC is not applied.

FIG. 2 is a diagram illustrated to describe a configuration example of amobile network system to which the MEC is applied.

FIG. 3 is a diagram illustrated to describe a configuration example of amobile network system to which the MEC is applied.

FIG. 4 is a diagram illustrated to describe an example of informationsynchronization using a centralized server.

FIG. 5 is a diagram illustrated to describe an example of informationsynchronization using P2P.

FIG. 6 is a diagram illustrated to describe an example of informationsynchronization to which the MEC is applied.

FIG. 7 is a diagram illustrated to describe an example of informationsynchronization to which the MEC is applied.

FIG. 8 is a diagram illustrated to describe an example of informationsynchronization to which the MEC is applied.

FIG. 9 is a diagram illustrated to describe an example of informationsynchronization to which the MEC is applied.

FIG. 10 is a diagram illustrated to describe an example of a screendisplayed by an application.

FIG. 11 is a block diagram illustrating a configuration example of aterminal device 100 according to an embodiment of the presentdisclosure.

FIG. 12 is a block diagram illustrating a functional configurationexample of an eNodeB 200 according to an embodiment of the presentdisclosure.

FIG. 13 is a block diagram illustrating a functional configurationexample of an MME 300 according to an embodiment of the presentdisclosure.

FIG. 14 is a flow diagram illustrating an operation example of a mobilenetwork according to an embodiment of the present disclosure.

FIG. 15 is a flow diagram illustrating an operation example of a mobilenetwork according to an embodiment of the present disclosure.

FIG. 16 is a flow diagram illustrating an operation example of a mobilenetwork according to an embodiment of the present disclosure.

FIG. 17 is a flow diagram illustrating an operation example of a mobilenetwork according to an embodiment of the present disclosure.

FIG. 18 is a flow diagram illustrating an operation example of a mobilenetwork according to an embodiment of the present disclosure.

FIG. 19 is a flow diagram illustrating an effect obtained by a mobilenetwork according to an embodiment of the present disclosure.

FIG. 20 is a flow diagram illustrating an effect obtained by a mobilenetwork according to an embodiment of the present disclosure.

FIG. 21 is a block diagram illustrating an example of a schematicconfiguration of a server 700 to which the technology according to thepresent disclosure is applicable.

FIG. 22 is a block diagram illustrating a first example of a schematicconfiguration of an eNB to which the technology according to the presentdisclosure is applicable.

FIG. 23 is a block diagram illustrating a second example of theschematic configuration of the eNB to which the technology according tothe present disclosure is applicable.

FIG. 24 is a block diagram illustrating an example of a schematicconfiguration of a smartphone 900 to which the technology according tothe present disclosure is applicable.

FIG. 25 is a block diagram illustrating an example of a schematicconfiguration of a car navigation device 920 to which the technologyaccording to the present disclosure is applicable.

MODE(S) FOR CARRYING OUT THE INVENTION

Hereinafter, (a) preferred embodiment(s) of the present disclosure willbe described in detail with reference to the appended drawings. In thisspecification and the appended drawings, components that havesubstantially the same function and structure are denoted with the samereference numerals, and repeated description of these components isomitted.

Moreover, description will be given in the following order.

1. Embodiment of present disclosure

1.1. System configuration example

1.2. Device configuration example

1.2.1. Configuration example of terminal device

1.2.2. Configuration example of base station

1.2.3. Configuration example of control entity

1.3. Operation example

2. Application examples

3. Concluding remarks

1. Embodiment of Present Disclosure 1.1. System Configuration Example

A configuration example of a system according to an embodiment of thepresent disclosure is now described.

Recent wireless communication environments are confronted with rapidincrease in data traffic. Then, in response to the rapid increase indata traffic, the improvement of capability of wireless access hasbecome urgent necessity.

As a technique for improving the capability of wireless access, thetechnique called MEC as described above is developed. The MEC is thetechnique in which cache data or an application is arranged in a basestation (eNodeB) and so the cache data is referred to from UE, or anapplication to be used by the UE is enabled (activated). This speeds upthe response time, which is the time taken from when the UE requestsdata to when it receives the data.

A mobile network system to which the MEC is not applied is compared to amobile network system to which the MEC is applied to describe the effectobtained by the MEC. FIG. 1 is a diagram illustrated to describe aconfiguration example of the mobile network system to which the MEC isnot applied. FIG. 1 illustrates a system including a radio accessnetwork (RAN) 10, an evolved packet core (EPC) 20, and a network 30,such as the Internet, outside the mobile network. The mobile networksystem illustrated in FIG. 1 is, in one example, a system compliant withLTE, LTE-Advanced, or other equivalent communication standards.

The RAN 10 illustrated in FIG. 1 is configured to include a terminaldevice (UE) 100 and eNodeBs 200 a, 200 b, and 200 c. In the followingdescription, in the case where there is no particular significance todistinguish among eNodeBs 200 a, 200 b, and 200 c, they are simplyreferred to as an eNodeB 200.

The terminal device 100 is, in one example, any mobile device used by auser, such as a smartphone (a high-end mobile phone) or a tabletterminal. The eNodeB 200 a, 200 b, and 200 c are individual basestations. Data is transmitted between the terminal device 100 and theeNodeB 200 a via a Uu interface, and data is transmitted between theeNodeB 200 a and the eNodeB 200 b and between the eNodeB 200 a and theeNodeB 200 c, via an X2 interface. The X2 interface is used for dataexchange upon handover and is used for the coordination of interferencebetween eNodeBs.

The EPC 20 illustrated in FIG. 1 is configured to include a mobilitymanagement entity (MME) 300, a home subscriber server (HSS) 400, aserving gateway (S-GW) 500, and a packet data network gateway (P-GW)600.

The S-GW 500 is an entity that is an anchor point for handover. The P-GW600 allocates an IP address to the terminal device 100. In addition, theS-GW 500 provides an IP address to be accessed to the outside of themobile network.

Data is transmitted between the MME 300 and the eNodeB 200 a via anS1-MME interface, between the MME 300 and the HSS 400 via an S6ainterface, and between the MME 300 and the S-GW 500 via an S11interface. Data is transmitted between the S-GW 500 and the eNodeB 200 avia an S1-U interface and between the S-GW 500 and the P-GW 600 via anS5 interface.

In the EPC, the control plane and the user plane are separated. The S-GW500 and the P-GW 600 are mainly related to the user plane, and the MME300 and the HSS 400 are related to the control plane. The S-GW 500 has afunction of holding user data to be an anchor point of handover even inthe configuration to which the MEC is not applied. On the other hand,the eNodeBs 200 a, 200 b, and 200 c have no function of holding userdata in related art but only have functions such as packetretransmission corresponding to the packet loss occurred in the Uuinterface, and so neither cache data nor applications are arranged.

The network 30 illustrated in FIG. 1 is configured to include a cacheserver 700 used to store cache data and a server device 800 used tostore actual data. Data is transmitted between the cache server 700 andthe P-GW 600 via an SGi interface.

In the mobile network to which the MEC is not applied as illustrated inFIG. 1, the data to be cached is placed in the network 30 outside theRAN 10 and the EPC 20 of the mobile network. Thus, the delay from theterminal device 100 arranged in the area of the RAN 10 to the cacheserver 700 causes a response from the cache server 700 to a request ofthe terminal device 100 to be delayed.

An example of a request of the terminal device 100 includes a staticdata downloading request, such as downloading of an image or a movie, byaccessing a hypertext transfer protocol (HTTP) server and a dynamicrequest, such as an operation on a specific application. Thus, it isnatural that the response to a request is faster when cache data orapplication is arranged in an entity (e.g., eNodeB 200 a in FIG. 1) nearthe terminal device 100.

Further, the delay depends on how far an entity passes through, ratherthan the distance between entities. In other words, the processing delaynecessary for an input unit that inputs data, a processing unit thatprocesses data, and an output unit that outputs data is added at eachentity as many as the number of entities, so the delay of the responsefrom the cache server 700 to the request of the terminal device 100increases.

Thus, the cache data or application is arranged in the eNodeB, and so itcan expected that the time of the response for the cache data to therequest of the terminal device 100 is reduced. FIG. 2 is a diagramillustrated to describe a configuration example of a system of a mobilenetwork to which the MEC is applied.

FIG. 2 illustrates a network configuration in which a cache server 700for cache data and an application is arranged in the eNodeB 200 a. Theconfiguration illustrated in FIG. 2 reduces the number of entitiesexisting between the terminal device 100 and the cache server 700 forcache data or an application. Thus, it can be expected for the mobilenetwork illustrated in FIG. 2 to achieve a response from the cacheserver 700 to the request of the terminal device 100 in a short time.

FIG. 3 is a diagram illustrated to describe a configuration example of asystem of a mobile network to which the MEC is applied. FIG. 3illustrates a configuration in which the cache server 700 is arranged inthe eNodeB 200 a and another cache server 700 is arranged in the S-GW500. In a case where there is a request from the terminal device 100, ifthere is no cache data in the eNodeB 200 a, the cache data stored in theS-GW 500 is used rather than fetching the original data from the serverdevice 800. In this way, the cache server 700 is arranged in each of theeNodeB 200 a and the S-GW 500, so it is expected that a response fromthe cache server 700 to the request of the terminal device 100 isachieved in a short time.

Even in the case where the cache server 700 transmits data, the cachedata is recognized through the HTTP header, and so it is necessary forsome applications that can be processed by HTTP to be activated by theeNodeB 200 (equipped with the function of the cache server 700). Inaddition, even in the case where a particular application is supplied tothe terminal device 100, it is also necessary for the correspondingapplication to be arranged in the eNodeB 200 (equipped with the functionof the cache server 700).

The application fails to be used in inactivated state (disabled) even inthe state in which the application is arranged in the eNodeB 200. Thus,it is important for the application to be activated, that is, is readyfor use, as well as to be arranged in the eNodeB 200.

The types of applications executed by the terminal device 100 arevarious, so it is a heavy burden for the eNodeB 200 (equipped with thefunction of the cache server 700) to keep all applications active(enabled state) at all times. Thus, it is reasonable for the eNodeB 200to activate the application when the terminal device 100, which uses theapplication, appears.

Further, for the cache data, in the case where data is not cached in thecache server 700 even if the cache server 700 is active, it may benecessary to fetch data eventually from the server device 800 in whichthe original data is stored.

Some applications may be necessary to keep their states insynchronization with each other by exchanging their internal statesafter the application is in an active state. In one example, in asynchronous network game application, it is necessary to keepinformation on where a character or the like is on the map synchronizedwith the application. In this case, the terminal devices 100simultaneously playing the network game belong to different eNodeBs 200,but requisite data is necessary to be cached in the eNodeB 200corresponding to each of these terminal devices 100. Further, it isnecessary to synchronize the state of the game applications arranged inthe eNodeBs 200 corresponding to these terminal devices 100. Thus, atthe eNodeB 200, the activation of the application, internal state of theapplication, and caching for the application are necessary to beperformed by causing it to be linked between the separated eNodeBs 200.

In general, a method of synchronizing information of a network game isroughly divided into server-centralized type and peer-to-peer (P2P)type. FIG. 4 is a diagram illustrated to describe an example ofinformation synchronization using the server-centralized type. Inaddition, FIG. 5 is a diagram illustrated to describe an example ofinformation synchronization using the P2P type.

The server-centralized type is a method in which logically one serverdevice 800 in the center achieves synchronization among the terminaldevices 100 a to 100 e of all users. In the server-centralized type, theresponse of the user far from the server device 800 is delayed, and theload on the server device 800 is also increased.

The P2P type is a method in which synchronization signals are directlyexchanged between users (between terminal devices serving as clients).The P2P type is suitable for the case of one-to-one or a case where thenumber of users is small, but it is not suitable for the battle gamewhere thousands or tens of thousands participate.

In the case where the application can be arranged in the eNodeB 200, itis possible to obtain advantages of the centralized type illustrated inFIG. 4 and the P2P type illustrated in FIG. 5 by synchronizing theapplications arranged in the eNodeB 200.

FIGS. 6 to 9 are diagrams illustrated to describe an example ofinformation synchronization to which the MEC is applied. FIG. 6illustrates an example in which the eNodeB 200 centrally synchronizesinformation between the terminal devices 100 and the server device 800centrally synchronizes information between the eNodeBs 200. FIG. 7illustrates an example in which the eNodeB 200 centrally synchronizesinformation between the terminal devices 100 and the server device 800synchronizes information between the eNodeBs 200 using the P2P type.FIG. 8 illustrates an example in which the eNodeB 200 centrallysynchronizes information between the terminal devices 100 and the serverdevice 800 placed in the EPC 20 centrally synchronizes informationbetween the eNodeBs 200. FIG. 9 illustrates an example the eNodeB 200centrally synchronizes information between the terminal devices 100, andinformation is synchronized between the eNodeBs 200 using the P2P typewhich directly loops back in the EPC 20.

In this way, in one example, an application is arranged in the eNodeB200 where the terminal device 100 participating in a network game islocated and the applications arranged in the eNodeB 200 are synchronizedwith each other in the server-centralized or P2P type. This allows theload on the server device 800 to be reduced, as compared with the caseof direct synchronization between a large number of terminal devices100.

FIG. 10 is a diagram illustrated to describe an example of a screendisplayed by an application, which is an example of a screen displayingthe positions of characters, which are operated by different users on amap, simultaneously on the map. In the case where it is necessary tosynchronize the positions of the characters on the map between theterminal devices 100 as illustrated in FIG. 10, the position on the mapof the game of the character operated on the terminal device 100belonging to one eNodeB 200 may be mapped on the map in the applicationof the eNodeB 200, and the position information of the integratedcharacter on the map may be arranged in synchronization with each otheron the map of another eNodeB 200. In other words, it is unnecessary foreven the terminal device 100 to perform updating directly on the map, sothe load on the network is reduced.

In the eNodeB 200, the information related to the user on the map in theapplication of each eNodeB 200 is updated. Thus, when the terminaldevice 100 accesses the map information of the eNodeB 200 as necessary,it is possible to update the screen of the game with a response timeshorter than the case of accessing the server device 800.

In this way, the arrangement of the cache data or application in theeNodeB 200 makes it possible to improve the response from the terminaldevice 100. However, in arranging the cache data or application in theeNodeB 200, it is necessary to consider the following points.

(1) Delay Due to Cache Data

As described above, it is effective to arrange the function of the cacheserver 700 in the eNodeB 200 close to the user to deliver datacorresponding to the request of the terminal device 100 to the user in ashort time.

However, the data, which has been not actually used by another terminaldevice 100 belonging to the eNodeB 20 even once, is typically notcached. The data, which has never been used by all the terminal devices100 belonging to the eNodeB 200, is not cached in the eNodeB 200. Thus,the terminal device 100 that accessed the data for the first time isnecessary to acquire data from a server (e.g., the S-GW 500 or theserver 800 arranged in a normal network outside the mobile network) thatis further away from the eNodeB 200 in the mobile network.

Thus, if data is not cached in the eNodeB 200, the response time whichis the time taken to deliver the data to the terminal device 100 in aresponse on the basis of the request of the terminal device 100 will beincreased.

Thus, in the case where the terminal device 100, which belongs to theeNodeB 200 but belonged to it in the past, attempts to acquire data,which has never been used by the terminal device 100, for the firsttime, there is no cache data in the eNodeB 200. Thus, the terminaldevice 100 will takes time to acquire data.

(2) Delay Due to Application Starting

The same applies to the case where an application of the eNodeB 200 isarranged. As described above, it is effective to arrange the serverwhere the application is arranged in the eNodeB 200 close to the user todeliver data corresponding to the request of the terminal device 100 tothe user in a short time.

However, simply arranging the application in the eNodeB 200 isinsufficient, and so it is necessary to activate the applicationarranged in the eNodeB 200 to which the terminal device 100 concernedwith the application belongs by causing it to be linked between theeNodeBs 200 and is necessary to be ready for use it.

In the case where there are the eNodeB 200 that activates an applicationand the eNodeB 200 that does not activate the application, it isconceivable that the response of the terminal device 100 belonging tothe eNodeB 200 that does not activate the application is delayed.Furthermore, the terminal device 100 is often in motion, so it isconceivable that the response of the terminal device 100 is delayedunless the application is activated in the eNodeB 200 serving as adestination by handover.

(3) Delay Due to Non-Synchronized Internal State of Application

There is a case in which the internal state of an application arrangedin the respective eNodeBs 200 is desired to be synchronized between therespective eNodeBs 200. Even if an application is arranged and is in anactive state, non-synchronization of the internal state may causeinconsistency between the terminal devices 100 using the applicationarranged in the respective eNodeBs 200. In one example, there areproblems in the following three use cases.

(Use Case 1)

A use case where the terminal device 100 belonging to an eNodeB 200 anda neighboring terminal device 100 belonging to an eNodeB 200 adjacentthereto are desired to use the same application is assumed. In oneexample, there may be a case where a plurality of small base stationsare installed at an event site. In this case, when a particular terminaldevice 100 uses an application corresponding to the event, if the sameapplication is not allowed to be used in the same manner by theplurality of small base stations, the response of the application isdelayed.

(Use Case 2)

A use case where a small cell (small base station) is arranged isassumed. The small cell has a function of switching between a normal onstate and an off state with reduced power consumption. In the off state,there is a feature such that a predetermined reference signal (referencesignal) is not transmitted. Even if the terminal device 100 does notmove from the place, the small cell to be connected to the terminaldevice may change frequently sometimes. In such a case, the applicationis necessary to be active in all the small cells.

In the case where a plurality of small cells are physically implementedin one device and only an antenna is implemented separately as a smallcell, the one device includes an application or data practically, sothere seems to be no problem with synchronization. However, if theapplication is not in an active state in each small cell implementedlogically, it is considered that a delay occurs depending on the smallcell accessed by the terminal device 100.

(Use Case 3)

In a network game, there is a case where thousands or tens of thousandsof users play the game while influencing each other in real time in onegame world. In this case, it is necessary to synchronize the internalstates of the application of a plurality of users. However, if theinternal states of the application are not synchronized between theeNodeBs 200, inconvenience due to a delay for synchronizing the data ornon-synchronization of data will occur.

In view of this, the person who conceived the present disclosure hasconducted intensive studies to provide a technology capable of furtherreducing the response time of the terminal device in the mobile networksystem to which the MEC is applied. Accordingly, the person whoconceived the present disclosure has developed the technology capable offurther reducing the response time of the terminal device in the mobilenetwork system to which the MEC is applied by determining a base stationin which data is held in advance and by causing the determined basestation to hold the data.

The configuration example of the system according to an embodiment ofthe present disclosure is described above. Subsequently, a configurationexample of a device according to an embodiment of the present disclosureis described in detail.

1.2. Device Configuration Example 1.2.1. Configuration Example ofTerminal Device

First, a configuration example of a terminal device 100 according to anembodiment of the present disclosure is described. FIG. 11 is a blockdiagram illustrating an exemplary configuration of the terminal device100 according to an embodiment of the present disclosure. Referring toFIG. 11, the terminal device 100 is configured to include an antennaunit 110, a wireless communication unit 120, a storage unit 130, and aprocessing unit 140.

(Antenna Unit 110)

The antenna unit 110 emits a signal output by the wireless communicationunit 120 to a space as a radio wave. In addition, the antenna unit 110converts a radio wave in a space into a signal and outputs the signal tothe wireless communication unit 120.

(Wireless Communication Unit 120)

The wireless communication unit 120 transmits and receives a signal. Inone example, the wireless communication unit 120 receives a downlinksignal from the eNodeB 200 and transmits an uplink signal to the eNodeB200.

(Storage Unit 130)

The storage unit 130 temporarily or permanently stores a program anddata that allow the terminal device 100 to operate. In the presentembodiment, the storage unit 130 stores, in one example, a program foran application running on the terminal device 100. The program or datastored in the storage unit 130 is read out, whenever necessary, by acontrol unit 143.

(Processing Unit 140)

The processing unit 140 allows the terminal device 100 to performvarious functions. The processing unit 140 includes an informationacquisition unit 141 and the control unit 143. Moreover, the processingunit 140 can further include other components in addition to thesecomponents. That is, the processing unit 140 can also perform otheroperations in addition to the operations of these components.

(Information Acquisition Unit 141)

The information acquisition unit 141 acquires various types ofinformation from a signal obtained from the radio wave received by theantenna unit 110. In the present embodiment, the information acquisitionunit 141 acquires a response to the request to the eNodeB 200. In oneexample, when the control unit 143 transmits, to the eNodeB 200, acontent acquisition request serving as a request signal to the eNodeB200, the information acquisition unit 141 acquires content serving as aresponse from the eNodeB 200.

(Control Unit 143)

The control unit 143 controls the operation of the terminal device 100.In the present embodiment, the terminal device 100 performs processingof causing the antenna unit 110 to transmit information on anapplication in which data is linked with another terminal device 100that communicates with the same eNodeB 200 or a different eNodeB 200 asor from the eNodeB 200 that communicates with the terminal device 100.The information sent from the terminal device 100 is transmitted to theMME 300 via the eNodeB 200. It is possible for the MME 300 to determinethe eNodeB 200 that causes the application to be activated using theinformation sent from the terminal device 100.

The example of the functional configuration of the terminal device 100according to an embodiment of the present disclosure is described above.Next, an example of a functional configuration of the eNodeB 200according to an embodiment of the present disclosure is described.

1.2.3. Configuration Example of Base Station

FIG. 12 is a block diagram illustrating an example of a functionalconfiguration of the eNodeB 200 according to an embodiment of thepresent disclosure. As illustrated in FIG. 12, the eNodeB 200 accordingto an embodiment of the present disclosure is configured to include anantenna unit 210, a wireless communication unit 220, a networkcommunication unit 230, a storage unit 240, and a processing unit 250.

(Antenna Unit 210)

The antenna unit 210 emits a signal output by the wireless communicationunit 220 to a space as a radio wave. In addition, the antenna unit 210converts a radio wave of a space into a signal and outputs the signal tothe wireless communication unit 220.

(Wireless Communication Unit 220)

The wireless communication unit 220 transmits and receives a signal. Inone example, the wireless communication unit 220 transmits a downlinksignal to terminal device and receives an uplink signal from terminaldevice.

(Network Communication Unit 230)

The network communication unit 230 transmits and receives information.In one example, the network communication unit 230 transmits informationto other nodes and receives information from other nodes. An example ofthe other node includes a core network and other base stations. In oneexample, the other node includes the MME 300.

(Storage Unit 240)

The storage unit 240 temporarily or permanently stores a program anddata that allow the eNodeB 200 to operate. In the present embodiment,the storage unit 240 stores cache data referred to by the eNodeB 200, orstores an application and data used by the application. The program ordata stored in the storage unit 240 is read out, whenever necessary, bythe control unit 253.

(Processing Unit 250)

The processing unit 250 allows the eNodeB 200 to perform variousfunctions. The processing unit 250 includes an information acquisitionunit 251 and the control unit 253. Moreover, the processing unit 250 canfurther include other components in addition to these components. Thatis, the processing unit 250 can also perform other operations inaddition to the operations of the components.

(Information Acquisition Unit 251)

The information acquisition unit 251 acquires information or a programthat allows the eNodeB 200 to operate, or acquires information receivedfrom other nodes. The information acquisition unit 251 can acquireinformation or a program that allows the eNodeB 200 to operate from thestorage unit 240. In addition, the information acquisition unit 251acquires cache data, a command for activating the application, and dataused by the application, which are transmitted from another eNodeB 200that is in linked state.

(Control Unit 253)

The control unit 253 controls the operation of the eNodeB 200. In thepresent embodiment, the control unit 253 performs processing ofreturning data in response to a request from the terminal device 100 orprocessing of linking data with another eNodeB 200 on the basis of anotification from the MME 300.

In one example, when there is a notification from the MME 300 that datais linked with another eNodeB 200, the control unit 253 executes controlso that the cache data referred to by the terminal device 100 or acommand for activating an application and data used by the applicationis forwarded to the other eNodeB 200 on the basis of the notification.

The eNodeB 200 performs forwarding of an applications or cache data toother eNodeBs 200 via the X2 interface. In addition, the eNodeB 200 alsotransmits a command for activation of the application via the X2interface. Moreover, in the case where the MME 300 instructs tocooperate with an eNodeB 200 that is separated to some extent, theeNodeB 200 forwards an application or cache data or sends a command foractivation of an application via the S-GW 500.

In some cases, an eNodeB 200 causes the cache data or the like to belinked with another eNodeB 200 via the X2 interface, and in other cases,it causes the cache data or the like to be linked with another eNodeB200 via the EPC 20. In the case where the cache data or the like isintended to be linked via the EPC 20, when the cache data or the like islinked with the other eNodeB 200, the control unit 253 may cause theserver device 800 to centrally link the cache data or the like, causethe eNodeBs 200 to link it with each other using P2P, cause the serverdevice 800 placed in the EPC 20 to centrally link it between the eNodeBs200, and cause the eNodeBs 200 to directly loop back with each otherusing P2P, as described with reference to FIGS. 6 to 9, respectively.

The example of the functional configuration of the eNodeB 200 accordingto an embodiment of the present disclosure is described above. Next, anexample of a functional configuration of the MME 300 according to anembodiment of the present disclosure is described.

1.2.3. Configuration Example of Control Entity

FIG. 13 is a block diagram illustrating an example of a functionalconfiguration of the MME 300 according to an embodiment of the presentdisclosure. As illustrated in FIG. 13, the MME 300 according to anembodiment of the present disclosure is configured to include acommunication unit 310, a storage unit 320, and a processing unit 330.

(Communication Unit 310)

The communication unit 310 transmits and receives information. In oneexample, the communication unit 310 transmits information to other nodesand receives information from other nodes. An example of the other nodeincludes a core network and a base station. In one example, the othernode includes the eNodeB 200.

In the present embodiment, the communication unit 310 notifies the NodeB200 determined by a control unit 333 that the cache data is held bylinkage or the application is activated under the control of the controlunit 333. The communication unit 310 can also function as an example ofa notification unit of the present disclosure.

(Storage Unit 320)

The storage unit 320 temporarily or permanently stores a program anddata that allow the MME 300 to operate. In one example, the storage unit320 temporarily or permanently stores the information acquired by aninformation acquisition unit 331.

The storage unit 320 may store data that is used by the control unit 333for various types of control. In one example, in a case where thecontrol unit 333 determines the eNodeB 200 to be linked on the basis ofgeographical conditions, the storage unit 320 may store geographicalinformation of the eNodeB 200. In one example, in a case where thecontrol unit 333 determines the eNodeB 200 to be linked on the basis ofthe attribute of the terminal device 100, the storage unit 320 may storeinformation on the attribute of the terminal device 100. The informationon the attribute of the terminal device 100 is typically stored in theHSS 400, and the storage unit 320 may store information on the attributeof the terminal device 100 that is acquired from the HSS 400 by theinformation acquisition unit 331.

(Processing Unit 330)

The processing unit 330 allows the MME 300 to perform various functions.The processing unit 330 includes the information acquisition unit 331and the control unit 333. Moreover, the processing unit 330 can furtherinclude other components in addition to these components. That is, theprocessing unit 330 can also perform other operations in addition to theoperations of the components.

(Information Acquisition Unit 331)

The information acquisition unit 331 acquires information that allowsthe MME 300 to operate and acquires information received from othernodes. The information acquisition unit 331 can acquire information or aprogram that allows the MME 300 to operate from the storage unit 320.

(Control Unit 333)

The control unit 333 controls the operation of the MME 300. The controlunit 333 can operate on the basis of the information acquired by theinformation acquisition unit 331. In the present embodiment, the controlunit 333 determines the eNodeB 200 that is caused to hold cache data oractivate an application on the basis of predetermined conditions. Thecontrol unit 333 may determine the eNodeB 200 that is caused to holdcache data or activate an application on the basis of the informationacquired by the information acquisition unit 331. In the followingdescription, the eNodeB 200 that is caused to hold cache data oractivate an application is also referred to as an eNodeB 200 to belinked.

There are various predetermined conditions used when the control unit333 determines the eNodeB 200. In one example, the control unit 333 maydetermine the eNodeB 200 to be linked on the basis of geographicalconditions. Examples of the geographical conditions include positioningwithin a predetermined range or the like. In addition, in one example,the control unit 333 may determine the eNodeB 200 to be linked on thebasis of content of a request from the terminal device 100, theattribute of the terminal device 100, or the like. In one example, thecontrol unit 333 may determine the eNodeB 200 specified by the terminaldevice 100 as the eNodeB 200 to be linked, or may determine the eNodeB200 to which another eNodeB 200 linked with the terminal device 100belongs as the eNodeB 200 to be linked.

The example of the functional configuration of the MME 300 according toan embodiment of the present disclosure is described above. Next, anexample of an operation of the mobile network according to an embodimentof the present disclosure is described.

1.3. Operation Example 1.3.1. First Operation Example

First, as a first operation example, an example is described in whichthe MME 300 or other management node (e.g., the HSS 400) previouslydetermines the eNodeB to be linked on the basis of geographicalconditions.

FIG. 14 is a flow diagram illustrating an operation example of themobile network according to an embodiment of the present disclosure.FIG. 14 illustrates an operation example in the case where the MME 300or other management node (e.g., the HSS 400) previously determines theeNodeB to be linked on the basis of geographical conditions.

The MME 300 determines an eNodeB to be linked, in one example, on thebasis of geographical conditions (step S101). The processing in stepS101 is executed by, in one example, the control unit 333. The MME 300may determine an eNodeB to be linked, in one example, on the conditionthat it exists in a predetermined area as a geographical condition, ormay determine an eNodeB to be linked on condition that it is locatedwithin a circle of a predetermined radius around a certain point. Inaddition, the MME 300 may determine an eNodeB to be linked on thecondition that the terminal device 100 is located within a range whereit is likely to move. In one example, the MME 300 may decide a rangewithin which the terminal device 100 is likely to move, in one example,on the basis of the history of position information of the terminaldevice 100, the history of connection to the eNodeB 200 in the past, orthe like. Alternatively, the MME 300 may decide the range on the basisof contract information of the terminal device 100. FIG. 14 illustratesan example in which the MME 300 determines the eNodeBs 200 a and 200 bas the eNodeBs to be linked.

The MME 300 can also determine an eNodeBs to be linked using variousother conditions. In one example, in a case where a target eNodeB is asmall cell whose power source is frequently switched on/off, the MME 300may determine a small cell located within the predetermined range as aneNodeB to be linked.

The MME 300, when determining an eNodeB 200 to be linked on the basis ofthe geographical condition, notifies the determined eNodeB 200 that itis determined as the eNodeB 200 to be linked (steps S102 and S103). Theprocessing in steps S102 and S103 is executed by, in one example, thecontrol unit 333 that causes the communication unit 310 to transmit thenotification. In FIG. 14, the eNodeBs 200 a and 200 b are determined aseNodeBs to be linked, and so the MME 300 notifies the eNodeBs 200 a and200 b of the result.

Then, when the terminal device 100 transmits a request for predeterminedcontent (referred to as content A) in the application layer to theeNodeB 200 a (step S104), the request is transferred from the eNodeB 200a to the server device 800 via the S-GW 500 and the P-GW 600. The serverdevice 800 returns a response for the content A in the application layerto the eNodeB 200 a (step S105). The eNodeB 200 a is notified that it isdetermined as the eNodeB to be linked from the MME 300, and caches thecontent A (step S106).

The eNodeB 200 a, when caching the content A returned from the serverdevice 800, returns a response for the content A in the applicationlayer to the terminal device 100 (step S107). Furthermore, the eNodeB200 a is notified that it is linked with the eNodeB 200 b from the MME300, and so decides to redirect the content A so that the content A iscaused to be cached in the eNodeB 200 b (step S108)

Then, the eNodeB 200 a transfers the content A via the X2 interface tocause the eNodeB 200 b to cache the content A (step S109). The eNodeB200 is notified that it is determined as the eNodeB to be linked fromthe MME 300, and so caches the content A transferred from eNodeB 200 a(step S110).

The eNodeBs 200 a and 200 b and the MME 300 execute the series ofoperations illustrated in FIG. 14, so it is possible for the eNodeBs 200a and 200 b to cache the content held by the server device 800 bycausing it to be linked between the eNodeBs 200 a and 200 b. Thus, whenthe terminal device 100 accesses the eNodeB 200 b and requests thecontent A by a request in the application layer, it is possible for theterminal device 100 to acquire the content A cached in the eNodeB 200 b.Thus, the eNodeBs 200 a and 200 b and the MME 300 execute the series ofoperations illustrated in FIG. 14, so it is possible to reduce theresponse time of the terminal device 100.

In FIG. 14, there is illustrated an example where the terminal device100 first accesses the eNodeB 200 a and so causes the eNodeBs 200 a and200 b to hold the cache data by causing it to be linked with each other.However, if the terminal device 100 first accesses the eNodeB 200 b, itis natural that the eNodeB 200 b acquires and caches data from theserver device 800, and transfers the cache data to the eNodeB 200 a viathe X2 interface. The operation of the eNodeBs 200 a and 200 b asdescribed above makes it possible to cause the eNodeBs 200 a and 200 bto hold the cache data by causing it to be linked with each other.

In some cases, an eNodeB 200 may cause the cache data or the like to belinked with another eNodeB 200 via the X2 interface, or in other cases,an eNodeB 200 may cause the cache data or the like to be linked withanother eNodeB 200 via the EPC 20. In the case where the cache data orthe like is intended to be linked via the EPC 20, when the eNodeB 200 acauses the cache data or the like to be linked with the other eNodeB200, the eNodeB 200 a may cause the server device 800 to centrally linkthe cache data or the like, cause the eNodeBs 200 to link it with eachother using P2P, cause the server device 800 placed in the EPC 20 tocentrally link it between the eNodeBs 200, and cause the eNodeBs 200 todirectly loop back with each other using P2P, as described withreference to FIGS. 6 to 9, respectively.

1.3.2. Second Operation Example

Subsequently, as a second operation example, an example is described inwhich the MME 300 or other management node (e.g., the HSS 400)determines an eNodeB to be linked on the basis of the attribute of theterminal device 100 that sends a request.

FIG. 15 is a flow diagram illustrating an operation example of themobile network according to an embodiment of the present disclosure.FIG. 15 illustrates an operation example in the case where the MME 300or other management node (e.g., the HSS 400) determines an eNodeB to belinked on the basis of the attribute of the terminal device 100 thatsends a request.

The information on the terminal device 100 is registered in the HSS 400in advance. The information on the terminal device 100 that isregistered in the HSS 400 may include, in one example, information ongeographical conditions, information on the contract that data relatedto a particular application is allowed to be cached, or the like. Thus,before the terminal device 100 issues a request in the applicationlayer, that is, at the time of setup of the EPS bearer, the MME 300acquiring the attribute of the terminal device 100 from the HSS 400makes it possible to determine an eNodeB to cache data of theapplication layer that is carried by the bearer.

When the terminal device 100 sends a request to activate the EPS bearer(step S111), the MME 300 acquires the attribute of the terminal device100 that sends the request from the HSS 400, and determines a range ofan eNodeB to be linked in association with the attribute of the terminaldevice 100 (step S112). The processing in step S112 is executed by, inone example, the control unit 333. FIG. 15 illustrates an example inwhich the eNodeBs 200 a and 200 b are determined as eNodeBs to be linkedby the MME 300.

It is possible for the MME 300 to decide to what extent the eNodeBs arenecessary to be linked by extracting geographical information of theterminal device 100 from the HSS 400. In addition, if there is acontract that data is allowed to be cached and information indicatinghow much adjacent eNodeB to be cached is written with the contractinformation stored in the HSS 400, it is possible for the MME 300 todetermine an eNodeB to be linked in accordance with the contractinformation.

Further, if the information on the terminal device 100 that is about toplay the same network game is registered in the MME 300 or the HSS 400,the MME 300 is capable of specifying an eNodeB to which the terminaldevices 100 simultaneously using the mobile network belong. Thus, theMME 300 is capable of determining these specified eNodeBs as the eNodeBsto be linked.

The MME 300, when determining an eNodeB to be linked in association withthe terminal device 100, notifies the determined eNodeB that it isdetermined as an eNodeB to be linked (steps S113 and S114). Theprocessing in steps S113 and S114 is executed by, in one example, thecontrol unit 333 that causes the communication unit 310 to transmit thenotification. In FIG. 15, the eNodeBs 200 a and 200 b are determined aseNodeBs to be linked, and so the MME 300 notifies the eNodeBs 200 a and200 b of the result.

The subsequent operation is similar to the procedure illustrated in FIG.14. In other words, when the terminal device 100 transmits a request forpredetermined content (referred to as content A) in the applicationlayer to the eNodeB 200 a (step S115), the request is transferred fromthe eNodeB 200 a to the server device 800 via the S-GW 500 and the P-GW600. The server device 800 returns a response for the content A in theapplication layer to the eNodeB 200 a (step S116). The eNodeB 200 a isnotified that it is determined as an eNodeB to be linked from the MME300, and caches the content A (step S117).

The eNodeB 200 a, when caching the content A returned from the serverdevice 800, returns a response for the content A in the applicationlayer to the terminal device 100 (step S118). Furthermore, the eNodeB200 a is notified that it is linked with the eNodeB 200 b from MME 300,and so decides to redirect the content A to cause the content A to becached in the eNodeB 200 b (step S119).

Then, the eNodeB 200 a transfers the content A via the X2 interface tocause the eNodeB 200 b to cache the content A (step S120). The eNodeB200 is notified that it is determined as an eNodeB to be linked from theMME 300, and so caches the content A transferred from eNodeB 200 a (stepS121).

In this second operation example, the range of the eNodeB to be linkedis determined in association with the attribute of the terminal device100 and the result is notified to the determined eNodeB from the MME300. Thus, it is possible to hold the cache data by causing it to belinked between a plurality of eNodeBs.

FIG. 15 also illustrates an example in the case where the terminaldevice 100 first accesses the eNodeB 200 a and so causes the eNodeBs 200a and 200 b to hold the cache data by causing it to be linked. However,if the terminal device 100 first accesses the eNodeB 200 b, it isnatural that the eNodeB 200 b acquires and caches data from the serverdevice 800 and transfers the cached data to the eNodeB 200 a via the X2interface. The operation of the eNodeBs 200 a and 200 b as describedabove makes it possible to cause the eNodeBs 200 a and 200 b to hold thecached data by causing it to be linked.

1.3.3. Third Operation Example

Subsequently, as a third operation example, an example is described inwhich the MME 300 or other management node (e.g., the HSS 400)determines an eNodeB to be linked on the basis of a request from theterminal device 100.

FIG. 16 is a flow diagram illustrating an operation example of themobile network according to an embodiment of the present disclosure.FIG. 16 illustrates an operation example in the case where the MME 300or other management node (e.g., the HSS 400) determines an eNodeB to belinked on the basis of a request from the terminal device 100.

The terminal device 100, which first intends to send a request in theapplication layer, can request a range of an eNodeB to be linked or thetype of an application that is desired to be linked from the MME 300,when the EPS bearer corresponding to the request is newly created. Inthe case where the request for the range of an eNodeB to be linked fromthe terminal device 100 is acceptable, the MME 300 sets the range of theeNodeB to be linked to each eNodeB.

When the terminal device 100 sends the range of the eNodeB to be linked(step S131), the MME 300 decides the range of the eNodeB to be linked onthe basis of the request (step S132). The processing in step S132 isexecuted by, in one example, the control unit 333. FIG. 16 illustratesan example in which the MME 300 determines eNodeBs 200 a and 200 b asthe eNodeBs to be linked on the basis of a request from the terminaldevice 100. Moreover, in FIG. 16, the terminal device 100 sends therange of the eNodeB to be linked, but the terminal device 100 may sendthe type of the application that is desired to be linked. The MME 300decides the range of the eNodeB to be linked on the basis of the type ofthe application that is desired to be linked.

The MME 300, when determining the eNodeB to be linked in associationwith the terminal device 100, notifies the determined eNodeB that it isdetermined as the eNodeB to be linked (steps S133 and S134). Theprocessing in steps S133 and S134 is executed, in one example, by thecontrol unit 333 that causes the communication unit 310 to transmit thenotification. In FIG. 16, the eNodeBs 200 a and 200 b are determined aseNodeBs to be linked, and so the MME 300 notifies the eNodeBs 200 a and200 b of the result.

The subsequent operation is similar to the procedure illustrated in FIG.14 or FIG. 15. In other words, when the terminal device 100 transmits arequest for predetermined content (referred to as content A) in theapplication layer to the eNodeB 200 a (step S135), the request istransferred from the eNodeB 200 a to the server device 800 via the S-GW500 and the P-GW 600. The server device 800 returns a response for thecontent A in the application layer to the eNodeB 200 a (step S136). TheeNodeB 200 a is notified that it is determined as an eNodeB to be linkedfrom the MME 300, and so caches the content A (step S137).

The eNodeB 200 a, when caching the content A returned from the serverdevice 800, returns a response for the content A in the applicationlayer to the terminal device 100 (step S138). Furthermore, eNodeB 200 ais notified that it is linked with the eNodeB 200 b from the MME 300,and so the eNodeB 200 a decides to redirect the content A so that thecontent A is caused to be cached in the eNodeB 200 b (step S139).

Then, the eNodeB 200 a transfers the content A via the X2 interface tocause the eNodeB 200 b to cache the content A (step S140). The eNodeB200 is notified that it is determined as an eNodeB to be linked from theMME 300, and so caches the content A transferred from eNodeB 200 a (stepS141).

1.3.4. Fourth Operation Example

Subsequently, as a fourth operation example, an example is described inwhich the MME 300 or other management node (e.g., the HSS 400)determines an eNodeB to be linked on the basis of the type of theapplication.

FIG. 17 is a flow diagram illustrating an operation example of themobile network according to an embodiment of the present disclosure.FIG. 17 illustrates an operation example in the case where the MME 300or other management node (e.g., the HSS 400) determines an eNodeB to belinked on the basis of the type of the application.

The MME 300 is also capable of changing the range of an eNodeB to belinked depending on the type of the application. The MME 300 determinesthe range of an eNodeBs to be linked, which is necessary for respectiveapplications in the application layer. The attribute of the applicationlayer do not necessarily fall within the range of linkage of eNodeBs,and it may be narrower or wider. The MME 300 or other management nodereceiving the attribute sets the range of the eNodeB to be linked toeach eNodeB.

When the terminal device 100 transmits a request for predeterminedcontent (referred to as content A) in the application layer to theeNodeB 200 a (step S151), the request is transferred from the eNodeB 200a via the S-GW 500 and the P-GW 600 to the server device 800. The serverdevice 800 requests the range of an eNodeB to be linked from the MME 300via the P-GW 600 by using signaling of the application layer (stepS152).

The MME 300, when receiving the request from the server device 800,determines the range of the eNodeB to be linked in association with theattribute of the terminal device 100 that requests the activation of theEPS bearer (step S153). The processing in step S153 is executed by, inone example, the control unit 333. FIG. 17 illustrates an example inwhich the MME 300 determines the eNodeBs 200 a and 200 b as the eNodeBsto be linked.

The MME 300, when determining the eNodeB to be linked in associationwith the terminal device 100, notifies the determined eNodeB that it isdetermined as the eNodeB to be linked (steps S154 and S155). Theprocessing in steps S154 and S155 are executed, in one example, by thecontrol unit 333 that causes the communication unit 310 to transmit thenotification. In FIG. 17, the eNodeBs 200 a and 200 b are determined aseNodeBs to be linked, and so the MME 300 notifies the eNodeBs 200 a and200 b of the result.

Then, the server device 800 returns a response for the content A in theapplication layer to the eNodeB 200 a (step S156). The eNodeB 200 a isnotified that it is determined as the eNodeB to be linked from the MME300, and so caches the content A (step S157)

The eNodeB 200 a, when caching the content A returned from the serverdevice 800, returns a response for the content A in the applicationlayer to the terminal device 100 (step S158). Furthermore, the eNodeB200 a is notified that it is linked with the eNodeB 200 b from the MME300, and so decides to redirect the content A so that the content A iscaused to be cached in the eNodeB 200 b (step S159).

Then, the eNodeB 200 a transfers the content A via the X2 interface tocause the eNodeB 200 b to cache the content A (step S160). The eNodeB200 is notified that it is determined as the eNodeB to be linked fromthe MME 300, and so caches the content A transferred from eNodeB 200 a(step S161).

1.3.5. Fifth Operation Example

Subsequently, as a fifth operation example, an example is described inwhich the MME 300 or other management node (e.g., the HSS 400)determines an eNodeB to be linked on the basis of information on anotherterminal device 100 b, which is specified from a terminal device 100 a.

FIG. 18 is a flow diagram illustrating an operation example of themobile network according to an embodiment of the present disclosure.FIG. 18 illustrates an operation example in the case where the MME 300or other management node (e.g., the HSS 400) determines an eNodeB to belinked in association with information on the other terminal device 100b specified from the terminal device 100 a.

The terminal device 100 a (or the server device 800) makes a request tothe MME 300 for the terminal device 100 b to be linked by usinginformation (IMSI or an ID for specifying a terminal device such as MACaddress) used to identify the terminal device 100 b to be linked (stepS171).

In the case where the terminal device 100 b is RRC connected to aparticular eNodeB (e.g., the eNodeB 200 b), the MME 300 is capable ofspecifying the eNodeB by exchange with the HSS 400.

Thus, the MIME 300 determines an eNodeB to be linked so that the eNodeB200 a is linked to cache it with the eNodeB 200 b that is RRC connected(step S172), and notifies the determined eNodeB that it is determined asthe eNodeB to be linked (steps S173 and S174).

Moreover, in the case where the terminal device 100 b is in RRC idlemode for a particular eNodeB (e.g., the eNodeB 200 b), the eNodeB 200 bperforms, in one example, paging to the terminal device 100 b. In thiscase, if there is a response from the terminal device 100 b, the MME 300sets the eNodeB 200 b as a target to be linked.

The subsequent operation is similar to the procedure illustrated in FIG.14 or 15. In other words, when the terminal device 100 transmits arequest for predetermined content (referred to as content A) in theapplication layer to the eNodeB 200 a (step S175), the request istransferred from the eNodeB 200 a to the server device 800 via the S-GW500 and the P-GW 600. The server device 800 returns a response for thecontent A in the application layer to the eNodeB 200 a (step S176). TheeNodeB 200 a is notified that it is determined as the eNodeB to belinked from the MME 300, and caches the content A (step S177).

The eNodeB 200 a, when caching the content A returned from the serverdevice 800, returns a response for the content A in the applicationlayer to the terminal device 100 (step S178). Furthermore, the eNodeB200 a is notified that it is linked with the eNodeB 200 b from MME 300,and so decides to redirect the content A to cause the content A to becached in the eNodeB 200 b (step S179).

Then, the eNodeB 200 a transfers the content A via the X2 interface tocause the eNodeB 200 b to cache the content A (step S180). The eNodeB200 is notified that it is determined as the eNodeB to be linked fromthe MME 300, and so caches the content A transferred from eNodeB 200 a(step S181).

As described above, the MME 300 determines an eNodeB that satisfies apredetermined condition as an eNodeB that is caused to manage the databy causing it to be linked and notifies the determined eNodeB that it isdetermined as the eNodeB, which is caused to manage the data by causingit to be linked. Each of the eNodeBs receiving the notification, whenacquiring data from the server in which the original data is stored,transfers the data to another eNodeB to be linked. These operations bythe MME 300 and the eNodeB 200 allow the terminal device 100 to improvethe response time from when the data is requested to when the data isacquired.

Subsequently, advantageous effects of an embodiment of the presentdisclosure are described. FIG. 19 is a flow diagram illustrated todescribe advantageous effects according to an embodiment of the presentdisclosure, and illustrates an operation example when the terminaldevice 100 accesses the eNodeB 200 b for the first time. The flowdiagram illustrated in FIG. 19 is based on the assumption that theeNodeB 200 b caches the data of the content A by any of theabove-described operations.

When the terminal device 100 transmits a request for predeterminedcontent (referred to as content A) in the application layer to theeNodeB 200 b (step S191), the eNodeB 200 b has already cached data ofthe content A, and so returns the cached data to the terminal device 100(step S192).

In other words, the eNodeB 200 b returns data to the terminal device 100without transferring the request from the eNodeB 200 b to the serverdevice 800 via the S-GW 500 and the P-GW 600. Thus, even when theterminal device 100 accesses the eNodeB 200 b for the first time, it ispossible to improve significantly the response time, as compared withthe case where the eNodeB 200 b does not cache data of the content A.

FIG. 20 is a flow diagram illustrated to describe advantageous effectsaccording to an embodiment of the present disclosure, and illustrates anoperation example when the eNodeBs 200 a and 200 b activate anapplication in accordance with an instruction of the MME 300.

The terminal device 100 a (or the server device 800) makes a request tothe MME 300 for the terminal device 100 b to be linked by usinginformation (IMSI or an ID for specifying a terminal device such as MACaddress) used to identify the terminal device 100 b to be linked (stepS201).

In the case where the terminal device 100 b is RRC connected to aparticular eNodeB (e.g., the eNodeB 200 b), the MME 300 is capable ofspecifying the eNodeB by exchange with the HSS 400.

Thus, the MME 300 determines an eNodeB to be linked so that the eNodeB200 a is linked to activate an application with the eNodeB 200 b that isRRC connected (step S202), and notifies the determined eNodeB that it isdetermined as the eNodeB to be linked (steps S203 and S205).

The eNodeBs 200 a and 200 b, which receive the notification from the MME300, activate the application on the basis of the notification (stepsS204 and S206).

Then, when the terminal device 100 a transmits a request for apredetermined application (referred to as content A) in the applicationlayer to the eNodeB 200 a (step S207), the eNodeB 200 a returns aresponse to the request to the terminal device 100 a (step S208). Inaddition, the eNodeB 200 a sends an instruction to update the internalstate of the application to the eNodeB 200 b to be linked (step S209).

The eNodeB 200 b, which updates the internal state of the application,transmits a response to the terminal device 100 b that belongs to theeNodeB 200 b and uses the same application (step S210).

The operations performed by the eNodeBs 200 a and 200 b as illustratedin FIG. 20 make it possible to update and supply the internal state ofthe application by causing it to be linked to the terminal device 100 aand 100 b that use the same application. In other words, the eNodeBs 200a and 200 b activate the same application, and so it is possible toreturn a response to the request from the terminal device 100 a to theterminal device 100 b in a short time.

2. Application Examples

The technology according to the present disclosure is applicable tovarious products. In one example, the MME 300 may be implemented as aserver of any type of server such as a tower server, a rack server, or ablade server. In addition, the MME 300 may be a control module mountedin a server (e.g., an integrated circuit module configured in one die,or a card or a blade inserted into a slot of a blade server).

Further, the eNodeB 200 may be implemented as any type of evolved node B(eNB), in one example, a macro eNB, a small eNB, or the like. The smalleNB may be an eNB that covers a smaller cell than a macro cell, such asa pico eNB, a micro eNB, or a home (femto) eNB. Alternatively, theeNodeB 200 may be implemented as other types of base stations such as anode B or a base transceiver station (BTS). The eNodeB 200 may include amain body that controls wireless communication (also referred to as abase station device) and one or more remote radio heads (RRHs) disposedin a place different from the main body. In addition, various types ofterminals to be described below may operate as the eNodeB 200 bytemporarily or semi-permanently executing the functions of a basestation.

In addition, in one example, the terminal device 100 may be implementedas a mobile terminal such as a smartphone, a tablet personal computer(PC), a notebook PC, a portable game terminal, a portable/dongle typemobile router, or a digital camera, or may be implemented as anin-vehicle terminal such as a car navigation device. In addition, theterminal device 100 may be implemented as a terminal that performsmachine-to-machine (M2M) communication (also referred to as a machinetype communication (MTC) terminal). Furthermore, the terminal device 100may be a wireless communication module mounted in such a terminal (e.g.,an integrated circuit module configured in one die).

2-1. Example of Application for Control Entity

FIG. 21 is a block diagram illustrating an example of a schematicconfiguration of a server 700 to which the technology according to thepresent disclosure is applicable. The server 700 is configured toinclude a processor 701, a memory 702, storage 703, a network interface704, and a bus 706.

The processor 701 may be, in one example, a central processing unit(CPU) or a digital signal processor (DSP) and controls the server 700 toperform various functions. The memory 702 includes a random accessmemory (RAM) and a read only memory (ROM) and stores programs executedby the processor 701 and data. The storage 703 can include a storagemedium such as a semiconductor memory or a hard disk.

The network interface 704 is a wired communication interface used toallow the server 700 to connect to a wired communication network 705.The wired communication network 705 may be a core network such as anevolved packet core (EPC), or may be a packet data network (PDN) such asthe Internet.

The bus 706 connects the processor 701, the memory 702, the storage 703,and the network interface 704 to each other. The bus 706 may include twoor more buses that operate at different speeds (e.g., a high-speed busand a low-speed bus).

In the server 700 illustrated in FIG. 21, one or more componentsincluded in the processing unit 330 described with reference to FIG. 13(the information acquisition unit 331 and/or the control unit 333) maybe mounted on the processor 701. As an example, a program for causing aprocessor to function as the one or more components (i.e., a program forcausing a processor to execute operations of the one or more components)may be installed in the server 700, and the processor 701 may executethe program. As another example, a module including the processor 701and the memory 702 may be equipped in the server 700, and the one ormore components may be mounted on the module. In this case, the modulemay store a program for causing a processor to function as the one ormore components in the memory 702 and the processor 701 may execute theprogram. The server 700 or the module may be provided as a deviceincluding the above-described one or more components as described above,or the program for causing a processor to function as the one or morecomponents may be provided. In addition, a readable recording medium inwhich the program is recorded may be provided.

2-2. Example of Application for Base Station First Application Example

FIG. 22 is a block diagram illustrating a first example of a schematicconfiguration of an eNB to which the technology according to the presentdisclosure is applicable. An eNB 800 includes one or more antennas 810and a base station device 820. Each antenna 810 and the base stationdevice 820 may be connected to each other via an RF cable.

Each of the antennas 810 includes a single or multiple antenna elements(e.g., multiple antenna elements that constitute an MIMO antenna), andis used for the base station device 820 to transmit and receive radiosignals. The eNB 800 may include the multiple antennas 810, asillustrated in FIG. 22. In one example, the multiple antennas 810 may becompatible with multiple frequency bands used by the eNB 800. Moreover,although FIG. 22 illustrates the example in which the eNB 800 includesthe multiple antennas 810, the eNB 800 may also include a single antenna810.

The base station device 820 is configured to include a controller 821, amemory 822, a network interface 823, and a wireless communicationinterface 825.

The controller 821 may be, in one example, a CPU or a DSP, and causesthe higher layer of the base station device 820 to operate variousfunctions. In one example, the controller 821 generates a data packetfrom data in a signal processed by the wireless communication interface825, and transfers the generated packet via the network interface 823.The controller 821 may bundle data from multiple base band processors togenerate a bundled packet, and may transfer the generated bundledpacket. The controller 821 may have logical functions of performingcontrol such as radio resource control, radio bearer control, mobilitymanagement, admission control, and scheduling. The control may beperformed in corporation with an eNB or a core network node in thevicinity. The memory 822 includes RAM and ROM, and stores a program thatis executed by the controller 821, and various types of control data(e.g., a list of terminals, transmission power data, and schedulingdata).

The network interface 823 is a communication interface for connectingthe base station device 820 to a core network 824. The controller 821may communicate with a core network node or another eNB via the networkinterface 823. In this case, the eNB 800 may be connected to the corenetwork node or the other eNB through a logical interface (e.g., S1interface or X2 interface). The network interface 823 may also be awired communication interface or a wireless communication interface forwireless backhaul. If the network interface 823 is the wirelesscommunication interface, the network interface 823 may use a higherfrequency band for wireless communication than a frequency band used bythe wireless communication interface 825.

The wireless communication interface 825 supports any cellularcommunication scheme such as Long Term Evolution (LTE) and LTE-Advanced,and provides radio connection to a terminal located in a cell of the eNB800 via the antenna 810. The wireless communication interface 825 maytypically include, in one example, a baseband (BB) processor 826 and anRF circuit 827. The BB processor 826 may perform, in one example,encoding/decoding, modulating/demodulating, andmultiplexing/de-multiplexing, and performs various types of signalprocessing of layers (e.g., L1, medium access control (MAC), radio linkcontrol (RLC), and a packet data convergence protocol (PDCP)). The BBprocessor 826 may have a part or all of the above-described logicalfunctions instead of the controller 821. The BB processor 826 may be amodule including a memory that stores a communication control program, aprocessor that executes the program, and the related circuits. Thefunction of the BB processor 826 may be changeable by updating theabove-described program. In addition, the module may be a card or ablade that is inserted into a slot of the base station device 820.Alternatively, the module may also be a chip that is mounted on the cardor the blade. The RF circuit 827 may include, in one example, a mixer, afilter, and an amplifier, and transmits and receives radio signals viathe antenna 810.

The wireless communication interface 825 may include the multiple BBprocessors 826, as illustrated in FIG. 22. In one example, the multipleBB processors 826 may be compatible with multiple frequency bands usedby the eNB 800. In addition, the wireless communication interface 825may include the multiple RF circuits 827, as illustrated in FIG. 22. Inone example, the multiple RF circuits 827 may be compatible withmultiple antenna elements. Moreover, although FIG. 22 illustrates theexample in which the wireless communication interface 825 includes themultiple BB processors 826 and the multiple RF circuits 827, thewireless communication interface 825 may include a single BB processor826 or a single RF circuit 827.

Second Application Example

FIG. 23 is a block diagram illustrating a second example of a schematicconfiguration of an eNB to which the technology according to the presentdisclosure is applicable. An eNB 830 includes one or more antennas 840,a base station device 850, and an RRH 860. Each antenna 840 and the RRH860 may be connected to each other via an RF cable. In addition, thebase station device 850 and the RRH 860 may be connected to each otherover a high-speed line such as an optical fiber cable.

Each of the antennas 840 includes a single or multiple antenna elements(e.g., multiple antenna elements that constitute an MIMO antenna), andis used for the RRH 860 to transmit and receive radio signals. The eNB830 may include the multiple antennas 840 as illustrated in FIG. 23. Inone example, the multiple antennas 840 may be compatible with multiplefrequency bands used by the eNB 830. Moreover, although FIG. 23illustrates the example in which the eNB 830 includes the multipleantennas 840, the eNB 830 may include a single antenna 840.

The base station device 850 is configured to include a controller 851, amemory 852, a network interface 853, a wireless communication interface855, and a connection interface 857. The controller 851, the memory 852,and the network interface 853 are respectively similar to the controller821, the memory 822, and the network interface 823 described withreference to FIG. 22.

The wireless communication interface 855 supports any cellularcommunication scheme such as LTE and LTE-Advanced, and provides wirelesscommunication to a terminal positioned in a sector corresponding to theRRH 860 via the RRH 860 and the antenna 840. The wireless communicationinterface 855 may typically include, in one example, a BB processor 856.The BB processor 856 is similar to the BB processor 826 described withreference to FIG. 22, except that the BB processor 856 is connected toan RF circuit 864 of the RRH 860 via the connection interface 857. Thewireless communication interface 855 may include the multiple BBprocessors 856, as illustrated in FIG. 23. In one example, the multipleBB processors 856 may be compatible with multiple frequency bands usedby the eNB 830. Moreover, although FIG. 23 illustrates the example inwhich the wireless communication interface 855 includes the multiple BBprocessors 856, the wireless communication interface 855 may include asingle BB processor 856.

The connection interface 857 is an interface for connecting the basestation device 850 (the wireless communication interface 855) to the RRH860. The connection interface 857 may also be a communication module forcommunication over the above-described high-speed line that connects thebase station device 850 (the wireless communication interface 855) tothe RRH 860.

Further, the RRH 860 is configured to include a connection interface 861and a wireless communication interface 863.

The connection interface 861 is an interface for connecting the RRH 860(the wireless communication interface 863) to the base station device850. The connection interface 861 may also be a communication module forcommunication over above-described high-speed line.

The wireless communication interface 863 transmits and receives radiosignals via the antenna 840. The wireless communication interface 863may typically include, in one example, the RF circuit 864. The RFcircuit 864 may include, in one example, a mixer, a filter, and anamplifier, and transmits and receives radio signals via the antenna 840.The wireless communication interface 863 may include multiple RFcircuits 864, as illustrated in FIG. 23. In one example, the multiple RFcircuits 864 may support multiple antenna elements. Moreover, althoughFIG. 23 illustrates the example in which the wireless communicationinterface 863 includes the multiple RF circuits 864, the wirelesscommunication interface 863 may also include a single RF circuit 864.

In the eNB 800 and the eNB 830 illustrated in FIGS. 22 and 23, one ormore components included in the processing unit 250 (the informationacquisition unit 251 and/or the control unit 253) described withreference to FIG. 11 may be mounted on the wireless communicationinterface 855 and/or the wireless communication interface 863.Alternatively, at least some of these components may be mounted on thecontroller 851. As an example, a module that includes a part (e.g., theBB processor 856) or all of the wireless communication interface 855and/or the controller 851 may be equipped in eNB 830, and the one ormore components may be mounted on the module. In this case, the modulemay store a program for causing the processor to function as the one ormore components (i.e., a program for causing the processor to executeoperations of the one or more components) and may execute the program.As another example, the program for causing the processor to function asthe one or more components may be installed in the eNB 830, and thewireless communication interface 855 (e.g., the BB processor 856) and/orthe controller 851 may execute the program. As described above, the eNB830, the base station device 850, or the module may be provided as adevice that includes the one or more components, and the program forcausing the processor to function as the one or more components may beprovided. In addition, a readable recording medium in which the programis recorded may be provided.

In addition, in the eNB 830 illustrated in FIG. 23, in one example, thewireless communication unit 220 described with reference to FIG. 11 maybe mounted on the wireless communication interface 863 (e.g., the RFcircuit 864). Moreover, the antenna unit 210 may be mounted on theantenna 840. In addition, the network communication unit 230 may bemounted on the controller 851 and/or the network interface 853.

2-3. Example of Application for Terminal Device First ApplicationExample

FIG. 24 is a block diagram illustrating an example of a schematicconfiguration of a smartphone 900 to which the technology according tothe present disclosure is applicable. The smartphone 900 is configuredto include a processor 901, a memory 902, storage 903, an externalconnection interface 904, a camera 906, a sensor 907, a microphone 908,an input device 909, a display device 910, a speaker 911, a wirelesscommunication interface 912, one or more antenna switches 915, one ormore antennas 916, a bus 917, a battery 918, and an auxiliary controller919.

The processor 901 may be, in one example, a CPU or a system on chip(SoC), and controls functions of the application layer or other layer ofthe smartphone 900. The memory 902 includes RAM and ROM, and stores aprogram that is executed by the processor 901, and data. The storage 903may include a storage medium such as a semiconductor memory or a harddisk. The external connection interface 904 is an interface forconnecting an external device such as a memory card or a universalserial bus (USB) device to the smartphone 900.

The camera 906 includes an image sensor such as a charge-coupled device(CCD) or a complementary-metal-oxide semiconductor (CMOS), and generatesa captured image. The sensor 907 may include a group of sensors such asa positioning sensor, a gyro sensor, a geomagnetic sensor, and anacceleration sensor. The microphone 908 converts sounds that are inputto the smartphone 900 to audio signals. The input device 909 includes,in one example, a touch sensor configured to detect touch onto a screenof the display device 910, a keypad, a keyboard, a button, or a switch,and receives an operation or an information input from a user. Thedisplay device 910 includes a screen such as a liquid crystal display(LCD) and an organic light-emitting diode (OLED) display, and displaysan output image of the smartphone 900. The speaker 911 converts audiosignals that are output from the smartphone 900 to sounds.

The wireless communication interface 912 supports any cellularcommunication scheme such as LTE and LTE-Advanced, and performs wirelesscommunication. The wireless communication interface 912 may typicallyinclude, in one example, a BB processor 913 and an RF circuit 914. TheBB processor 913 may perform, in one example, encoding/decoding,modulating/demodulating, and multiplexing/de-multiplexing, and performsvarious types of signal processing for wireless communication.Meanwhile, the RF circuit 914 may include, in one example, a mixer, afilter, and an amplifier, and transmits and receives radio signals viathe antenna 916. The wireless communication interface 912 may also be aone-chip module that has the BB processor 913 and the RF circuit 914integrated thereon. The wireless communication interface 912 may includethe multiple BB processors 913 and the multiple RF circuits 914, asillustrated in FIG. 24. Moreover, although FIG. 24 illustrates theexample in which the wireless communication interface 912 includes themultiple BB processors 913 and the multiple RF circuits 914, thewireless communication interface 912 may also include a single BBprocessor 913 or a single RF circuit 914.

Furthermore, the wireless communication interface 912 may support othertypes of wireless communication schemes such as a short-distancewireless communication scheme, a near field communication scheme, and awireless local area network (LAN) scheme, in addition to a cellularcommunication scheme. In this case, the BB processor 913 and the RFcircuit 914 may be included depending on each wireless communicationscheme.

Each of the antenna switches 915 switches connection destinations of theantennas 916 between multiple circuits (e.g., circuits for differentwireless communication schemes) included in the wireless communicationinterface 912.

Each of the antennas 916 includes a single or multiple antenna elements(e.g., multiple antenna elements that constitute an MIMO antenna), andis used for the wireless communication interface 912 to transmit andreceive radio signals. The smartphone 900 may include the multipleantennas 916, as illustrated in FIG. 24. Moreover, although FIG. 24illustrates the example in which the smartphone 900 includes themultiple antennas 916, the smartphone 900 may also include a singleantenna 916.

Furthermore, the smartphone 900 may be configured to include the antenna916 suitable for each wireless communication scheme. In this case, theantenna switch 915 may be omitted from the configuration of thesmartphone 900.

The bus 917 connects the processor 901, the memory 902, the storage 903,the external connection interface 904, the camera 906, the sensor 907,the microphone 908, the input device 909, the display device 910, thespeaker 911, the wireless communication interface 912, and the auxiliarycontroller 919 to each other. The battery 918 supplies power to eachblock of the smartphone 900 illustrated in FIG. 24 via feeder linesshown partially by dashed lines in the figure. The auxiliary controller919 causes the smartphone 900 to operate a minimum necessary function,in one example, in a sleep mode.

In the smartphone 900 illustrated in FIG. 24, one or more componentsincluded in the processing unit 140 (the information acquisition unit141 and/or the control unit 143) described with reference to FIG. 10 maybe mounted on the wireless communication interface 912. Alternatively,at least some of these components may be mounted on the processor 901 orthe auxiliary controller 919. As an example, a module that includes apart (e.g., the BB processor 913) or all of the wireless communicationinterface 912, the processor 901, and/or the auxiliary controller 919may be equipped in the smartphone 900, and the one or more componentsmay be mounted on the module. In this case, the module may store aprogram for causing the processor to function as the one or morecomponents (i.e., a program for causing the processor to executeoperations of the one or more components) and may execute the program.As another example, the program for causing the processor to function asthe one or more components may be installed in the smartphone 900, andthe wireless communication interface 912 (e.g., the BB processor 913),the processor 901, and/or the auxiliary controller 919 may execute theprogram. As described above, the smartphone 900 or the module may beprovided as a device that includes the one or more components, and theprogram for causing the processor to function as the one or morecomponents may be provided. In addition, a readable recording medium inwhich the program is recorded may be provided.

In addition, in the smartphone 900 illustrated in FIG. 24, in oneexample, the wireless communication unit 120 described with reference toFIG. 10 may be mounted on the wireless communication interface 912(e.g., the RF circuit 914). Moreover, the antenna unit 110 may bemounted on the antenna 916.

Second Application Example

FIG. 25 is a block diagram illustrating an example of a schematicconfiguration of a car navigation device 920 to which the technologyaccording to the present disclosure is applicable. The car navigationdevice 920 is configured to include a processor 921, a memory 922, aglobal positioning system (GPS) module 924, a sensor 925, a datainterface 926, a content player 927, a storage medium interface 928, aninput device 929, a display device 930, a speaker 931, a wirelesscommunication interface 933, one or more antenna switches 936, one ormore antennas 937, and a battery 938.

The processor 921 may be, in one example, a CPU or a SoC, and controlsthe car navigation device 920 to perform a navigation function and otherfunctions. The memory 922 includes RAM and ROM, and stores a programexecuted by the processor 921, and data.

The GPS module 924 uses GPS signals received from a GPS satellite tomeasure a position (e.g., latitude, longitude, and altitude) of the carnavigation device 920. The sensor 925 may include a group of sensorssuch as a gyro sensor, a geomagnetic sensor, and a barometric sensor.The data interface 926 is connected to, in one example, an in-vehiclenetwork 941 via a terminal that is not shown, and acquires datagenerated by the vehicle, such as vehicle speed data.

The content player 927 reproduces content stored in a storage medium(e.g., a CD and a DVD) that is inserted into the storage mediuminterface 928. The input device 929 includes, in one example, a touchsensor configured to detect touch onto a screen of the display device930, a button, or a switch, and receives an operation or an informationinput from a user. The display device 930 includes a screen such as aLCD or an OLED display, and displays an image of the navigation functionor content that is reproduced. The speaker 931 outputs the navigationfunction or the content that is reproduced as sounds.

The wireless communication interface 933 supports any cellularcommunication scheme such as LET and LTE-Advanced, and performs wirelesscommunication. The wireless communication interface 933 may typicallyinclude, in one example, a BB processor 934 and an RF circuit 935. TheBB processor 934 may perform, in one example, encoding/decoding,modulating/demodulating, and multiplexing/de-multiplexing, and performsvarious types of signal processing for wireless communication.Meanwhile, the RF circuit 935 may include, in one example, a mixer, afilter, and an amplifier, and transmits and receives radio signals viathe antenna 937. The wireless communication interface 933 may be aone-chip module having the BB processor 934 and the RF circuit 935integrated thereon. The wireless communication interface 933 may includethe multiple BB processors 934 and the multiple RF circuits 935, asillustrated in FIG. 25. Moreover, although FIG. 25 illustrates theexample in which the wireless communication interface 933 includes themultiple BB processors 934 and the multiple RF circuits 935, thewireless communication interface 933 may also include a single BBprocessor 934 or a single RF circuit 935.

Furthermore, the wireless communication interface 933 may support othertypes of wireless communication schemes such as a short-distancewireless communication scheme, a near field communication scheme, and awireless LAN scheme, in addition to a cellular communication scheme. Inthis case, the wireless communication interface 933 may include the BBprocessor 934 and the RF circuit 935 depending on each wirelesscommunication scheme.

Each of the antenna switches 936 switches connection destinations of theantennas 937 between multiple circuits (e.g., circuits for differentwireless communication schemes) included in the wireless communicationinterface 933.

Each of the antennas 937 includes a single or multiple antenna elements(e.g., multiple antenna elements that constitute an MIMO antenna), andis used for the wireless communication interface 933 to transmit andreceive radio signals. The car navigation device 920 may include themultiple antennas 937, as illustrated in FIG. 25. Moreover, althoughFIG. 25 illustrates the example in which the car navigation device 920includes the multiple antennas 937, the car navigation device 920 mayalso include a single antenna 937.

Furthermore, the car navigation device 920 may be configured to includethe antenna 937 suitable for each wireless communication scheme. In thatcase, the antenna switches 936 may be omitted from the configuration ofthe car navigation device 920.

The battery 938 supplies power to each block of the car navigationdevice 920 illustrated in FIG. 25 via feeder lines shown partially bydashed lines in the figure. The battery 938 accumulates power suppliedform the vehicle.

In the car navigation device 920 illustrated in FIG. 25, one or morecomponents included in the processing unit 140 (the informationacquisition unit 141 and/or the control unit 143) described withreference to FIG. 10 may be mounted on the wireless communicationinterface 933. Alternatively, at least some of these components may bemounted on the processor 921. As an example, a module that includes apart (e.g., the BB processor 934) or all of the wireless communicationinterface 933 and/or the processor 921 may be equipped in the carnavigation device 920, and the one or more components may be mounted onthe module. In this case, the module may store a program for causing theprocessor to function as the one or more components (i.e., a program forcausing the processor to execute operations of the one or morecomponents) and may execute the program. As another example, the programfor causing the processor to function as the one or more components maybe installed in the car navigation device 920, and the wirelesscommunication interface 933 (e.g., the BB processor 934) and/or theprocessor 921 may execute the program. As described above, the carnavigation device 920 or the module may be provided as a device thatincludes the one or more components, and the program for causing theprocessor to function as the one or more components may be provided. Inaddition, a readable recording medium in which the program is recordedmay be provided.

In addition, in the car navigation device 920 illustrated in FIG. 25,the wireless communication unit 120 described with reference to FIG. 10,in one example, may be mounted on the wireless communication interface933 (e.g., the RF circuit 935). Moreover, the antenna unit 110 may bemounted on the antenna 937.

Further, the technology according to the present disclosure may also beimplemented as an in-vehicle system (or a vehicle) 940 including one ormore blocks of the car navigation device 920, the in-vehicle network941, and a vehicle module 942. In other words, the in-vehicle system (ora vehicle) 940 may be provided as a device that includes the one or morecomponents included in the processing unit 140. The vehicle module 942generates vehicle data such as vehicle speed, engine speed, and troubleinformation, and outputs the generated data to the in-vehicle network941.

3. Concluding Remarks

According to an embodiment of the present disclosure as described above,there is provided a mobile communication system for causing a pluralityof eNodeBs selected by the MME to be linked. The MME determines aplurality of eNodeB to be linked on the basis of a predeterminedcondition, for example, positional condition, attribute of the terminaldevice, attribute of another terminal specified by the terminal device,or the like.

According to the embodiments of the present disclosure, it is possibleto arrange the function of the application server or the cache server toan entity (e.g. eNodeB or S-GW) close to the terminal device of themobile network. The arrangement of the functions of the applicationserver or cache server to an entity close to the terminal device of themobile network makes it possible to transmit data with less delay to theterminal device. In addition, the arrangement of the function of theapplication server or cache server to an entity close to the terminaldevice of the mobile network makes it possible to improve the quality ofsynchronization between applications running on a plurality of terminaldevice.

Moreover, although the example in which the communication systemcomplies with LTE or LTE-A has been described in an embodiment of thepresent disclosure, the present disclosure is not limited to thisexample. The communication system may be, in one example, a systemcomplying with other communication standards.

In addition, processing steps in processes of the present specificationmay not necessarily be executed in a time series manner in the orderdescribed in the flow diagrams or sequence diagrams. The processingsteps in the processes may also be executed, in one example, in adifferent order from the order described in the flow diagrams orsequence diagrams, or may be executed in parallel.

Furthermore, a computer program for causing a processor (e.g., a CPU, aDSP, etc.) provided in a device (e.g., the terminal device, the basestation, the control entity, or a module thereof) of the presentspecification to function as the device (i.e., a computer program forcausing the processor to execute operations of components of theabove-described device) can also be created. In addition, a recordingmedium in which the computer program is recorded may be provided.Moreover, a device that includes a memory storing the computer programand one or more processors that can execute the computer program (e.g.,a finished product or a module for a finished product (a component, aprocessing circuit, a chip, or the like) may also be provided. Inaddition, a method including operations of one or more components of thedevice (e.g., the information acquisition unit and/or the control unit)is also included in the technology according to the present disclosure.

The preferred embodiment(s) of the present disclosure has/have beendescribed above with reference to the accompanying drawings, whilst thepresent disclosure is not limited to the above examples. A personskilled in the art may find various alterations and modifications withinthe scope of the appended claims, and it should be understood that theywill naturally come under the technical scope of the present disclosure.

Further, the effects described in this specification are merelyillustrative or exemplified effects, and are not limitative. That is,with or in the place of the above effects, the technology according tothe present disclosure may achieve other effects that are clear to thoseskilled in the art from the description of this specification.

Additionally, the present technology may also be configured as below.

(1)

A control device including:

a control unit configured to determine a base station from among aplurality of base stations on the basis of a predetermined condition,the base station causing data on an application used by a terminaldevice to be linked, the terminal device wirelessly communicating withthe base station; and

a notification unit configured to notify all base stations determined bythe control unit that the data is caused to be linked.

(2)

The control device according to (1), further including:

an acquisition unit configured to acquire information from a terminaldevice that communicates with a base station,

in which the control unit determines a base station that satisfies apredetermined condition by using information acquired by the acquisitionunit from the terminal device.

(3)

The control device according to (2),

in which the predetermined condition is a base station specified fromthe terminal device.

(4)

The control device according to (2),

in which the predetermined condition is a base station with whichanother terminal device linked with the terminal device wirelesslycommunicates.

(5)

The control device according to (1),

in which the predetermined condition is that a base station is locatedwithin a predetermined range.

(6)

The control device according to (5),

in which the predetermined condition is that a base station in which anon state and an off state can be switched is located within apredetermined range.

(7)

The control device according to (1),

in which the predetermined condition is that a base station is locatedwithin a range within which the terminal device is likely to move.

(8)

The control device according to any of (1) to (7),

in which the control unit determines a base station that causes cachedata referred to by the terminal device to be linked.

(9)

The control device according to any of (1) to (7),

in which the control unit determines a base station that causesactivation of an application to be linked.

(10)

The control device according to any of (1) to (7),

in which the control unit determines, depending on an application to beactivated, a base station that causes activation of the application tobe linked.

(11)

A base station including:

an acquisition unit configured to acquire a notification that causesdata on an identical application to be linked with another base station;and

a control unit configured to cause the data to be linked with the otherbase station depending on a request from a terminal device on the basisof the notification acquired by the acquisition unit.

(12)

The base station according to (11),

in which the control unit causes cache data referred to by the terminaldevice to be linked with the other base station.

(13)

The base station according to (11),

in which the control unit causes data on an application updateddepending on the request from the terminal device to be linked with theother base station.

(14)

The base station according to any of (11) to (13),

in which the control unit causes the data to be linked with the otherbase station peer to peer.

(15)

The base station according to any of (11) to (13),

in which the control unit causes the data to be linked with the otherbase station via a server device.

(16)

The base station according to (15),

in which the server device is provided outside a core network.

(17)

The base station according to (15),

in which the server device is provided inside a core network.

(18)

A terminal device including:

a control unit configured to notify a core network of information on anapplication in which data is linked with another terminal device thatcommunicates with a base station identical or different to or from abase station which communicates with the terminal device.

(19)

A control method including:

determining a base station from among a plurality of base stations onthe basis of a predetermined condition, the base station causing data onan application used by a terminal device to be linked, the terminaldevice wirelessly communicating with the base station; and

notifying all determined base stations that the data is caused to belinked.

(20)

A control method of a base station, the control method including:

acquiring a notification that causes data on an identical application tobe linked with another base station; and

causing the data to be linked with the other base station on the basisof the notification acquired by the acquisition unit.

(21)

A control method of a terminal device, the control method including:

notifying a core network of information on an application in which datais linked with another terminal device that communicates with a basestation identical or different to or from a base station whichcommunicates with the terminal device.

(22)

A computer program causing a computer to execute:

determining a base station from among a plurality of base stations onthe basis of a predetermined condition, the base station causing data onan application used by a terminal device to be linked, the terminaldevice wirelessly communicating with the base station; and

notifying all determined base stations that the data is caused to belinked.

(23)

A computer program causing a computer to execute:

acquiring a notification that causes data on an identical application tobe linked with another base station; and

causing the data to be linked with the other base station on the basisof the notification acquired by the acquisition unit.

(24)

A computer program causing a computer to execute:

notifying a core network of information on an application in which datais linked with another terminal device that communicates with a basestation identical or different to or from a base station whichcommunicates with the terminal device.

REFERENCE SIGNS LIST

-   100 a, 100 b terminal device-   200 a, 200 b, 200 c eNodeB-   300 MME

The invention claimed is:
 1. A control device comprising: processingcircuitry configured to determine at least a first base station and asecond base station to hold application-related data related with anapplication program used by a terminal device from among a plurality ofbase stations based on a predetermined condition, the terminal devicewirelessly communicating with at least one of the determined first andsecond base stations: and] notify the determined first and second basestations to hold the application-related data such that the determinedfirst and second base stations activate the application program beforeat least one of the determined first and second base stations wirelesslycommunicates with the terminal device using an application layerregarding the activated application program, and that an internal stateof the application program is linked between the determined first andsecond base stations; wherein the predetermined condition is that a basestation is located within a predetermined range; wherein thepredetermined condition is that a base station in which an on state andan off state can be switched is located within a predetermined range. 2.The control device according to claim 1, wherein the processingcircuitry is configured to: acquire information from the terminal devicethat communicates with at least one of the determined first and secondbase stations, determine the first and second base stations that satisfythe predetermined condition by using the information acquired from theterminal device.
 3. The control device according to claim 2, wherein thepredetermined condition is a base station specified from the terminaldevice.
 4. The control device according to claim 2, wherein thepredetermined condition is a base station with which another terminaldevice linked with the terminal device wirelessly communicates.
 5. Thecontrol device according to claim 1, wherein the predetermined conditionis that a base station is located within a range within which theterminal device is likely to move.
 6. The control device according toclaim 1, wherein the processing circuitry is configured to determine thefirst and second base stations that cause cache data referred to by theterminal device to be linked.
 7. The control device according to claim1, wherein the processing circuitry is configured to determine the firstand second base stations that cause activation of the applicationprogram to be linked.
 8. The control device according to claim 1,wherein the processing circuitry is configured to determine, dependingon the application program to be activated, the first and second basestations that cause activation of the application program to be linked.9. A control method comprising: determining, using processing circuitry,at least a first base station and a second base station to holdapplication-related data related with an application program used by aterminal device from among a plurality of base stations based on apredetermined condition, the terminal device wirelessly communicatingwith at least one of the determined first and second base stations: andnotifying the determined first and second base stations to hold theapplication-related data such that the determined first and second basestations activate the application program before at least one of thedetermined first and second base stations wirelessly communicates withthe terminal device using an application layer regarding the activatedapplication program, and that an internal state of the applicationprogram is linked between the determined first and second base stations;wherein the predetermined condition is that a base station is locatedwithin a predetermined range; wherein the predetermined condition isthat a base station in which an on state and an off state can beswitched is located within a predetermined range.
 10. The control deviceaccording to claim 1, wherein the application program is an applicationprogram of a synchronous network game application and the internal stateincludes information on where a character is located within a map of thenetwork game application.